home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Performance Co-Pilot 1.3
/
SGI Performance Co-Pilot 1.3.iso
/
dist
/
pcp.idb
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pmgadgets.z.z
/
pmgadgets.z
/
pmgadgets
Wrap
Text File
|
1997-04-03
|
33KB
|
595 lines
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
NNNNAAAAMMMMEEEE
ppppmmmmggggaaaaddddggggeeeettttssss - a miniature graphical performance metrics viewer
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
ppppmmmmggggaaaaddddggggeeeettttssss [----CCCC] [----cccc _c_o_n_f_i_g] [----ddddeeeeffffaaaauuuullllttttffffoooonnnntttt _f_o_n_t] [----iiiinnnnffffooooffffoooonnnntttt _f_o_n_t] [----hhhh _h_o_s_t]
[----nnnn _n_a_m_e_s_p_a_c_e] [----tttt _u_p_d_a_t_e] [----zzzzoooooooommmm _f_a_c_t_o_r] [_s_t_a_n_d_a_r_d _X_1_1 _o_p_t_i_o_n_s]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ppppmmmmggggaaaaddddggggeeeettttssss creates a small window containing a collection of graphical
gadgets driven by performance metrics supplied by the Performance Co-
Pilot (PCP) framework. Any numeric metric supported by PCP can be
displayed. The layout of the gadgets and which performance metrics lie
behind them are specified in a configuration file. The configuration
file syntax and gadgets are described in detail below. Performance
metrics from several different hosts may be displayed simultaneously in
the same window.
ppppmmmmggggaaaaddddggggeeeettttssss is typically run on an existing configuration file or in
conjunction with an application that automatically generates a
configuration file. For example ppppmmmmggggiiiirrrriiiixxxx(1) generates a configuration
file for various IRIX performance metrics and feeds it to ppppmmmmggggaaaaddddggggeeeettttssss.
The ----cccc option specifies the configuration file for ppppmmmmggggaaaaddddggggeeeettttssss to read.
Only one configuration file file should be specified. If no
configuration file is specified, ppppmmmmggggaaaaddddggggeeeettttssss reads one from standard input.
If standard input is a terminal, a message warning the user what is
expected is printed. The warning message may be suppressed by specifying
---- as the configuration file.
The ----CCCC option will parse the configuration file and exit before
displaying the ppppmmmmggggaaaaddddggggeeeettttssss window. Any errors in the configuration file
are displayed. This is useful for testing ppppmmmmggggaaaaddddggggeeeettttssss with different
configuration files for correctness.
The ----ddddeeeeffffaaaauuuullllttttffffoooonnnntttt option overrides the default font used for label
gadgets. Gadgets that do not explicitly specify a font in the
configuration file are drawn using the default font. Unless this option
is used to override it, the default font used is 6x10. The ----iiiinnnnffffooooffffoooonnnntttt
option may be used to override the font used in the information windows.
Unless this option is used to override it, the font used is 6x10. _f_o_n_t
should be a valid X11 font specification.
The ----hhhh option (or its synonym ----hhhhoooossssttttnnnnaaaammmmeeee) specifies the name of a default
host for ppppmmmmggggaaaaddddggggeeeettttssss to obtain performance metrics from. Performance
metrics specified in the configuration file have an optional host name
part. If the optional host name is not supplied, the default host will
be used. If no ----hhhh option appears on the command line, localhost is used
as the default host.
Normally ppppmmmmggggaaaaddddggggeeeettttssss operates on the default Performance Metrics Namespace
(PMNS), however if the ----nnnn option (or its synonym ----nnnnaaaammmmeeeessssppppaaaacccceeee) is specified
an alternative namespace is loaded from the file _n_a_m_e_s_p_a_c_e.
PPPPaaaaggggeeee 1111
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
An update interval for each gadget may be given explicitly in the
configuration file. If it is not specified there, the default update
interval specified by the ----tttt (or its synonym ----ddddeeeellllttttaaaa) is used. _u_p_d_a_t_e
should be a real or integral number of seconds. If this option is not
specified, one second is used for the default update time.
The ----zzzzoooooooommmm option may be used to specify an integral magnification factor.
Each gadget in the configuration file will have its size and position
multiplied by _f_a_c_t_o_r. The zoom factor does not apply to text; the ----
ddddeeeeffffaaaauuuullllttttffffoooonnnntttt and ----iiiinnnnffffooooffffoooonnnntttt options must be used to change to font used to
draw text.
ppppmmmmggggaaaaddddggggeeeettttssss also accepts many of the standard X Window System options (see
the options section of XXXX(1)). Each of the command line options described
above may also be specified as an X11 resource. The resource names are
the long form of the option name (e.g. delta for ----tttt). The application
class name for ppppmmmmggggaaaaddddggggeeeettttssss is PmGadgets.
ppppmmmmggggaaaaddddggggeeeettttssss reads its configuration file, contacts the Performance Metrics
Collector Daemon (PMCD) on each host mentioned in the configuration file
and validates that the performance metrics required are available. If a
host or performance metric/instance is not available at start-up time,
ppppmmmmggggaaaaddddggggeeeettttssss will print an error message and exit.
Once the configuration file has been processed ppppmmmmggggaaaaddddggggeeeettttssss creates a small
top-level window and displays a collection of small graphical gadgets
representing the performance metrics. The gadgets are updated according
to the update intervals specified in the configuration file and the
command line. If a gadget's metrics are unavailable, the gadget is
grayed out.
Pressing the right mouse button inside the window brings up a popup menu
which allows one to terminate ppppmmmmggggaaaaddddggggeeeettttssss. Pressing the escape key (Esc)
with the mouse pointer in the window will also terminate the application.
Pressing the middle mouse button over one of the gadgets in the window
will bring up a popup menu containing a list of actions for the gadget,
if appropriate. Each gadget may have its own action list or share an
action list with other gadgets. The action lists are defined in the
configuration file. If there is a default action defined for a gadget,
double clicking on the gadget with the left mouse button invokes the
default action.
Gadgets that display performance metrics' values will always have an Info
action, which will create a small window containing the names of the
metrics being displayed by the gadget along with their current values.
This can also be displayed by positioning the mouse pointer over the
gadget and pressing the space bar. Note that each metric specification
contains the host name. This can be used to determine which host is
being monitored if several ppppmmmmggggaaaaddddggggeeeettttssss windows are visible.
PPPPaaaaggggeeee 2222
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
ppppmmmmggggaaaaddddggggeeeettttssss is designed to take up a minimal amount of space on the screen.
For this reason, only the most rudimentary window frame is drawn around
it. Text scaling is not supported by ppppmmmmggggaaaaddddggggeeeettttssss so the window may not be
resized while it is running. The ----zzzzoooooooommmm option may be used to produce a
magnified view.
CCCCOOOONNNNFFFFIIIIGGGGUUUURRRRAAAATTTTIIIIOOOONNNN FFFFIIIILLLLEEEE SSSSYYYYNNNNTTTTAAAAXXXX
The configuration file consists of an optional header and a list of
clauses. To make parsing easy, all reserved words begin with the
underscore character (____). Comments begin with the #### character and finish
at the end of the same line. Identifiers consist of an alphabetic
character followed by zero or more alphanumeric characters. In the
descriptions below, brackets (e.g. [optional bit]) are used to indicate
optional parts of clauses. Repetition is indicated with ellipses (...).
Lexical elements in bold should appear verbatim (e.g. [[[[ means use a
literal bracket rather than indicating an optional component of a
clause). Strings should be delimited by double quotes (e.g. """"xxxxccccoooonnnnffffiiiirrrrmmmm
----tttt ''''nnnnooootttt iiiimmmmpppplllleeeemmmmeeeennnntttteeeedddd''''""""). For convenience, the double quotes may be
omitted if the string is a valid identifier.
The optional header must be the first line in the configuration file that
isn't a comment or blank line. It consists of ppppmmmmggggaaaaddddggggeeeettttssss 1111
Action lists are used to build popup menus for gadgets.
____aaaaccccttttiiiioooonnnnssss _n_a_m_e (((( _a_c_t_i_o_n ...))))
Creates an action list called _n_a_m_e. Each _a_c_t_i_o_n should be of the form:
_a_c_t_i_o_n__n_a_m_e _a_c_t_i_o_n__s_t_r_i_n_g [____ddddeeeeffffaaaauuuulllltttt]
_a_c_t_i_o_n__n_a_m_e specifies a name for the action. This name will be used in
the menu that is created for the action list. _a_c_t_i_o_n__s_t_r_i_n_g specifies a
shell command to be executed when the action is selected from the menu.
_a_c_t_i_o_n__n_a_m_e and _a_c_t_i_o_n__s_t_r_i_n_g should both be strings. If ____ddddeeeeffffaaaauuuulllltttt is
present, it signifies the default action for the action list. There may
be only one default action in an action list.
Color lists are used to conveniently name a group of colors. This allows
similar gadgets to share a group of colors.
____ccccoooolllloooorrrrlllliiiisssstttt _n_a_m_e (((( _c_o_l_o_r__n_a_m_e ... ))))
Creates a list of colors called _n_a_m_e, which must be a valid identifier.
Each _c_o_l_o_r__n_a_m_e should be a valid X11 colour specification. If the
specification is not a valid identifier, it should be enclosed in double
quotes (e.g. """"rrrrggggbbbb::::ffffffffffffffff////0000////0000""""). For those that speak English rather than
American, ____ccccoooolllloooouuuurrrrlllliiiisssstttt is accepted as an alternative spelling of
____ccccoooolllloooorrrrlllliiiisssstttt....
PPPPaaaaggggeeee 3333
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
Legends are used to associate colors with numeric thresholds. Legends
are used to color-code numeric performance metric values.
____lllleeeeggggeeeennnndddd _n_a_m_e (((( _t_h_r_e_s_h_o_l_d ... ))))
Creates a legend called _n_a_m_e, which must be a valid identifier. Each
_t_h_r_e_s_h_o_l_d should be of the form
_n_u_m_b_e_r _c_o_l_o_r__n_a_m_e
or
____ddddeeeeffffaaaauuuulllltttt _c_o_l_o_r__n_a_m_e
_n_u_m_b_e_r may be either a floating point or integral value. When a
performance metric's value is to be represented as a color using a
legend, the color corresponding to the greatest _n_u_m_b_e_r in the legend less
than or equal to the metric's value is used. If the metric's value is
less than the smallest threshold, the ____ddddeeeeffffaaaauuuulllltttt color is used.
The position and size of a gadget is given using a _g_e_o_m_e_t_r_y__s_p_e_c, which
must be of the following form:
_x__p_o_s _y__p_o_s _w_i_d_t_h _h_e_i_g_h_t
_x__p_o_s and _y__p_o_s are integers that specify the position of the top left
corner of the gadget, relative to the top left corner of the window. X
values increase from left to right and Y values increase from top to
bottom. _w_i_d_t_h and _h_e_i_g_h_t should be positive integers. All units are in
pixels.
ppppmmmmggggaaaaddddggggeeeettttssss adds a margin to the bottom and right edges of its window. The
margin at the right edge is the same as the X position of the leftmost
gadget in the configuration file. Similarly, the bottom margin is the Y
position of the gadget with the minimum Y position.
The line gadget is just a horizontal or vertical line, with no underlying
performance metrics:
____lllliiiinnnneeee _g_e_o_m_e_t_r_y__s_p_e_c [_a_c_t_i_o_n_s]
The _g_e_o_m_e_t_r_y__s_p_e_c is the bounding box of the line, which will be filled.
E.g. to create a horizontal line 2 pixels high and 8 pixels wide at (5,
5) one would use a _g_e_o_m_e_t_r_y__s_p_e_c of 5 5 8 2. To create a vertical line
of the same thickness and length starting at the same point, the
_g_e_o_m_e_t_r_y__s_p_e_c would be 5 5 2 8. _a_c_t_i_o_n_s is optional and should be of the
form:
____aaaaccccttttiiiioooonnnnssss _n_a_m_e
PPPPaaaaggggeeee 4444
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
where _n_a_m_e specifies the name of a previously defined action list. If
present, the action list defines the contents of the popup menu under
mouse button two.
A label gadget specifies a piece of text. Only a single line of text may
be displayed by a label gadget. A label specification should be of the
form:
____llllaaaabbbbeeeellll _x__p_o_s _y__p_o_s _t_e_x_t [_f_o_n_t__s_p_e_c] [_a_c_t_i_o_n_s]
_x__p_o_s and _y__p_o_s specify the baseline origin of the label, not the top
left corner. _t_e_x_t is the label text; normally _t_e_x_t would be enclosed in
double quotes, however these may be omitted if _t_e_x_t is a valid
identifier. _f_o_n_t__s_p_e_c is a valid X Window System font name. If the font
name is not a valid identifier it should be enclosed in double quotes.
Refer to the XXXX(1) manual page for details of font naming. If the
_f_o_n_t__s_p_e_c is omitted, the default font specified on the command line is
used. If no default font was specified, the font 6x10 is used. _a_c_t_i_o_n_s
is optional and should specify the name of a previously defined action
list.
Performance metrics specifications usually appear in configuration files.
A _m_e_t_r_i_c__s_p_e_c has the form:
[_h_o_s_t:]metric[[[[[_i_n_s_t_a_n_c_e]]]]]
Where _h_o_s_t (and its accompanying colon) are optional and specify the host
from which the metric will be fetched. If no host is specified in the
configuration file, the default host is used. If no default host was
specified on the command line, the default host is localhost. _m_e_t_r_i_c
specifies a PCP performance metric name. _i_n_s_t_a_n_c_e must be enclosed in
brackets if it is present. It specifies which instance of the
performance metric is required. The instance must be specified in double
quotes if it is not a valid identifier. If _m_e_t_r_i_c has instances (is not
a single-valued metric), an instance must be specified. There is no
instance wildcarding.
The bar gadget displays a single performance metric value. It is a
rectangle that is filled from left to right or bottom to top in
proportion to the ratio of the metric's value to some maximum. The
maximum may be either a fixed number specified in the configuration file,
or the highest value of the metric seen so far. A bar gadget
specification has the form:
____bbbbaaaarrrr _g_e_o_m_e_t_r_y__s_p_e_c [_u_p_d_a_t_e] ____mmmmeeeettttrrrriiiicccc _m_e_t_r_i_c__s_p_e_c [_b_a_r__d_e_t_a_i_l ...]
[_b_a_r__c_o_l_o_r] [_a_c_t_i_o_n_s]
_u_p_d_a_t_e specifies an optional update interval for the gadget. It should
have the form
PPPPaaaaggggeeee 5555
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
____uuuuppppddddaaaatttteeee _d_e_l_t_a
A new value of the underlying performance metric is fetched every _d_e_l_t_a
seconds and the gadget is redrawn in accord. _b_a_r__d_e_t_a_i_l specifies either
an orientation (____hhhhoooorrrriiiizzzzoooonnnnttttaaaallll or vvvveeeerrrrttttiiiiccccaaaallll) or a bound. A bound consists of
____mmmmiiiinnnniiiimmmmuuuummmm, ____mmmmiiiinnnn, ____mmmmaaaaxxxxiiiimmmmuuuummmm or ____mmmmaaaaxxxx followed by a numeric value.
Contradictory _b_a_r__d_e_t_a_i_ls are not permitted.
If no bounds are specified, the gadget dynamically adjusts its maximum to
the greatest value of the metric that has been fetched. The default
minimum is zero. If a maximum is specified, it is used as an initial
maximum value, but if a greater value for the metric is fetched, the
bar's maximum will be increased accordingly. The same is true for the
bar's minimum. For example if no minimum is specified and the value of
the metric fetched is -10, the bar's minimum is adjusted from 0 (the
default) to -10. The proportion of the bar that is filled is the ratio
of two differences: the metric's current value minus the minimum and the
maximum minus the minimum.
If the word ____ffffiiiixxxxeeeedddd appears before ____mmmmaaaaxxxxiiiimmmmuuuummmm the maximum and minimum will
not be adjusted in this way. If the metric's value exceeds the fixed
maximum, a contrasting arrowhead is drawn in the completely filled bar.
If the metric's value falls below the fixed minimum a contrasting
arrowhead is drawn in the unfilled bar. It is not possible to have a
fixed maximum and a floating minimum or vice versa.
_b_a_r__c_o_l_o_r is optional and should have the form
____ccccoooolllloooouuuurrrr _c_o_l_o_r__n_a_m_e
Where _c_o_l_o_r__n_a_m_e is a valid X11 colour specification. If the
specification is not a valid identifier, it should be enclosed in double
quotes (e.g. """"rrrrggggbbbb::::ffffffffffffffff////0000////0000""""). For those that speak English rather than
American, ____ccccoooolllloooouuuurrrr is accepted as an alternative spelling of ____ccccoooolllloooorrrr....
_a_c_t_i_o_n_s is optional and should specify the name of a previously defined
action list.
If no value is available for the bar gadget's performance metric, the
gadget is grayed out.
The multibar gadget is similar to the bar gadget, but displays several
performance metrics at the same time. Each is allocated a color and the
gadget's rectangle is filled with an amount of each colour proportional
to the ratio of the corresponding performance metric's contribution to a
maximum value. The maximum may be a fixed value, the sum of the current
values of the gadget's metrics (utilization) or the greatest sum of the
gadget's metrics seen so far. A multibar gadget specification has the
form:
____mmmmuuuullllttttiiiibbbbaaaarrrr _g_e_o_m_e_t_r_y__s_p_e_c [_u_p_d_a_t_e] _m_e_t_r_i_c_s__l_i_s_t [_s_c_a_l_i_n_g] ____ccccoooolllloooorrrrlllliiiisssstttt _c_o_l_o_r_s
[_a_c_t_i_o_n_s]
PPPPaaaaggggeeee 6666
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
_u_p_d_a_t_e specifies an optional update interval for the gadget as described
above. _m_e_t_r_i_c_s__l_i_s_t should have the form
____mmmmeeeettttrrrriiiiccccssss (((( _m_e_t_r_i_c__s_p_e_c ... ))))
If no _s_c_a_l_i_n_g is specified, the multibar gadget plots each metric's
contribution to the greatest sum of metric values seen so far. The
maximum is initially set to a small positive value (0.000001). If a
_s_c_a_l_i_n_g of the form
[____ffffiiiixxxxeeeedddd] ____mmmmaaaaxxxxiiiimmmmuuuummmm _n_u_m_b_e_r
is specified, different semantics are used. If ____ffffiiiixxxxeeeedddd appears, the fixed
maximum specified by _n_u_m_b_e_r is used. If the sum of the metrics exceeds
the maximum, the gadget is drawn stippled with the quantity of each
colour in proportion to the contribution of the corresponding metric to
the sum of the metrics values. If the sum is less than the maximum, the
gadget will be drawn normally. If ____ffffiiiixxxxeeeedddd is omitted and a non-zero
maximum is specified, it specifies an initial maximum sum, but this
maximum will be adjusted if a higher sum is observed. If ____ffffiiiixxxxeeeedddd is
omitted and a maximum of zero is specified, the maximum will be set to
the sum of the metrics' current values every time the metrics are
fetched. This shows each metric's contribution as a fraction of the
current sum of all of the metrics' values. If the sum of the metrics in
such a multibar is zero, the multibar is grayed out. _c_o_l_o_r_s should
specify the name of a previously defined color list. Metrics in the
metrics list are paired with the corresponding entry in the color list.
The two lists should be the same length. The information window for a
multibar gadget contains the metric names and the corresponding colors.
_a_c_t_i_o_n_s is optional and should specify the name of a previously defined
action list.
The bargraph gadget displays a simple xxxxllllooooaaaadddd(1) style strip chart of a
performance metric's values over time. A bargraph gadget specification
should have the form:
____bbbbaaaarrrrggggrrrraaaapppphhhh _g_e_o_m_e_t_r_y__s_p_e_c [_u_p_d_a_t_e] ____mmmmeeeettttrrrriiiicccc _m_e_t_r_i_c__s_p_e_c [_s_c_a_l_i_n_g ... ]
[_a_c_t_i_o_n_s]
A history of _w_i_d_t_h - 1 values of the the performance metric's values are
displayed on the bargraph (_w_i_d_t_h is taken from the _g_e_o_m_e_t_r_y__s_p_e_c). The
oldest value appears at the left and new values are added to the right,
pushing older values to the left. _u_p_d_a_t_e specifies an optional update
interval for the gadget as described above. _s_c_a_l_i_n_g should be either
____mmmmaaaaxxxxiiiimmmmuuuummmm or ____mmmmiiiinnnniiiimmmmuuuummmm followed by a number to specify an initial upper
and/or lower bound for the bargraph. The minimum and maximum are
dynamically adjusted to the most extreme values of the underlying
performance metric seen so far. A maximum or minimum that has scrolled
off the left edge of the bargraph will continue to exert its effect. By
default, the minimum bound is zero. Normally the height of the bar drawn
at a point is proportional to the ratio of difference between the
metric's value there and its lowest historical value to the greatest
PPPPaaaaggggeeee 7777
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
metric range seen so far. The metric range is the difference between the
historical maximum and minimum. If no value was available for the
underlying metric a stippled, gray bar, the full height of the bargraph
is drawn.
If the word ____ffffiiiixxxxeeeedddd appears before ____mmmmaaaaxxxxiiiimmmmuuuummmm the maximum and minimum will
not be adjusted in this way. If the metric's value exceeds the fixed
maximum, a contrasting coloured segment is drawn at the top of a
completely filled bar. If the metric's value falls below the fixed
minimum a contrasting segment is drawn where the bottom of the bar would
normally appear. It is not possible to have a fixed maximum and a
floating minimum or vice versa.
_a_c_t_i_o_n_s is optional and should specify the name of a previously defined
action list.
The LED gadget is a threshold-based representation of a performance
metric. As the metric exceeds some numeric threshold a different colour
is drawn. A LED gadget specification has the form:
____lllleeeedddd _g_e_o_m_e_t_r_y__s_p_e_c [_u_p_d_a_t_e] ____mmmmeeeettttrrrriiiicccc _m_e_t_r_i_c__s_p_e_c ____lllleeeeggggeeeennnndddd _n_a_m_e [_a_c_t_i_o_n_s]
_u_p_d_a_t_e specifies an optional update interval for the gadget as described
above. _n_a_m_e should specify a previously defined legend. _a_c_t_i_o_n_s is
optional and should specify the name of a previously defined action list.
EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
Running ppppmmmmggggiiiirrrriiiixxxx(1) with the ----ccccoooonnnnffffiiiigggg flag causes it to print its
configuration file to standard output rather than feeding it to
ppppmmmmggggaaaaddddggggeeeettttssss.
FFFFIIIILLLLEEEESSSS
////vvvvaaaarrrr////ppppccccpppp////ppppmmmmnnnnssss////* default PMNS specification files
////uuuussssrrrr////lllliiiibbbb////XXXX11111111////aaaapppppppp----ddddeeeeffffaaaauuuullllttttssss////PPPPmmmmGGGGaaaaddddggggeeeettttssss
X11 application default resources
////vvvvaaaarrrr////ppppccccpppp////lllliiiibbbb////ppppmmmmggggaaaaddddggggeeeettttssss----aaaarrrrggggssss
Shell procedures that assist in the creation of
front-end scripts for pmgadgets.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ppppmmmmggggiiiirrrriiiixxxx(1), ppppmmmmiiiinnnnffffoooo(1), ppppmmmmccccdddd(1), XXXX(1).
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
Various errors will be generated in response to invalid configuration
files. Unavailable hosts, metrics or instances may also produce error
messages.
EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
Front-end tools using /_v_a_r/_p_c_p/_l_i_b/_p_m_g_a_d_g_e_t_s-_a_r_g_s are will report error
messages and warings using xxxxccccoooonnnnffffiiiirrrrmmmm(1) if $$$$DDDDIIIISSSSPPPPLLLLAAAAYYYY is set, otherwise
diagnostic output is written to standard error. If the $$$$PPPPCCCCPPPP____UUUUSSSSEEEE____SSSSTTTTDDDDEEEERRRRRRRR
environment variable is set, diagnostic messages are forced to standard
PPPPaaaaggggeeee 8888
PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111)))) PPPPMMMMGGGGAAAADDDDGGGGEEEETTTTSSSS((((1111))))
error.
CCCCAAAAVVVVEEEEAAAATTTTSSSS
If any of the performance metrics in the configuration file are not
available, ppppmmmmggggaaaaddddggggeeeettttssss will not start.
There are hard-wired limitations on the number of hosts, metrics and
instances specified in the configuration file. There can only be at most
1111000022224444 hosts, 222255556666 metrics and 4444000099996666 instances. Multiple occurences of the
same instances (e.g. irix.disk.dev.total["dks0d1"]) also get counted in
this number. If any of the limits is exceeded, the program will halt
with the appropriate error message.
There is currently no way to pass the ----hhhh option through to programs
specified in an action list. Programs that generate configuration files
automatically must explicitly generate actions that pertain to a remote
host. For example ppppmmmmggggiiiirrrriiiixxxx(1) uses its ----hhhh option to generate actions that
refer to the remote host.
If the time required to fetch performance metrics exceeds the update
interval for the metrics, ppppmmmmggggaaaaddddggggeeeettttssss may not have time to (re)draw the
gadgets before the next fetch begins. In pathological cases there may
not even be time to process user input.
PPPPaaaaggggeeee 9999